Crash notification between debuggers

ABSTRACT

Crash notification between debuggers, including: initiating, by a first debugger, a first debug session of a first application; detecting, by the first debugger, an error condition in the first application; determining, by the first debugger, whether any variables utilized by the first application are related to variables utilized by a second application, wherein the second application is being debugged in a second debug session by a second debugger; and communicating, by the first debugger to a second debugger, information associated with the error condition in the first application.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically,methods, apparatus, and products for crash notification betweendebuggers.

2. Description of Related Art

The development of the EDVAC computer system of 1948 is often cited asthe beginning of the computer era. Since that time, computer systemshave evolved into extremely complicated devices. Today's computers aremuch more sophisticated than early systems such as the EDVAC. Computersystems typically include a combination of hardware and softwarecomponents, application programs, operating systems, processors, buses,memory, input/output devices, and so on. As advances in semiconductorprocessing and computer architecture push the performance of thecomputer higher and higher, more sophisticated computer software hasevolved to take advantage of the higher performance of the hardware,resulting in computer systems today that are much more powerful thanjust a few years ago.

In today's computing environments, separate application programs ofteninteract with one another. A client application program and a serverapplication program that communicate with one another is one example.One class of problems that occur in a distributed environment is createdby incorrect data being propagated to other programs comprising thedistributed application. In many cases this bad data can actually causeseveral programs running on different systems to crash. Debugging suchapplications may be difficult as the debuggers do not understand theinterdependencies of each program.

SUMMARY OF THE INVENTION

Methods, apparatus, and products for crash notification betweendebuggers, including: initiating, by a first debugger, a first debugsession of a first application; detecting, by the first debugger, anerror condition in the first application; determining, by the firstdebugger, whether any variables utilized by the first application arerelated to variables utilized by a second application, wherein thesecond application is being debugged in a second debug session by asecond debugger; and communicating, by the first debugger to a seconddebugger, information associated with the error condition in the firstapplication.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of example embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of example embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 sets forth a block diagram of automated computing machinerycomprising an example computer useful in crash notification betweendebuggers according to embodiments of the present invention.

FIG. 2 sets forth a flow chart illustrating an example method for crashnotification between debuggers according to embodiments of the presentinvention.

FIG. 3 sets forth a flow chart illustrating an additional example methodfor crash notification between debuggers according to embodiments of thepresent invention.

FIG. 4 sets forth a flow chart illustrating an additional example methodfor crash notification between debuggers according to embodiments of thepresent invention.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Example methods, apparatus, and products for crash notification betweendebuggers in accordance with the present invention are described withreference to the accompanying drawings, beginning with FIG. 1. FIG. 1sets forth a block diagram of automated computing machinery comprisingan example computer (152) useful in crash notification between debuggersaccording to embodiments of the present invention. The computer (152) ofFIG. 1 includes at least one computer processor (156) or ‘CPU’ as wellas random access memory (168) (‘RAM’) which is connected through a highspeed memory bus (166) and bus adapter (158) to processor (156) and toother components of the computer (152).

Stored in RAM (168) is a first debugger (202), a module of computerprogram instructions utilized to test and debug other computer programs,such as a first application (204). The first debugger (202) may beconfigured such that a user can step through a target computer programto identify execution flow of the program, to determine the value ofvariables utilized by the program, and to identify crashes and othererrors generated during the execution of the program, and so on.

In the example of FIG. 1, the first debugger (202) can carry out crashnotification between debuggers by initiating a first debug session (206)of the first application (204). The first application (204) may beembodied as a computer program that includes a set of computer programinstructions. In such an example, initiating a first debug session (206)of the first application (204) can enable a user to execute the firstapplication (204) one instruction at a time, to execute all instructionsof the first application (204) that reside between a set of breakpoints,and otherwise examine the execution of the first application (204).

In the example of FIG. 1, the first debugger (202) can further carry outcrash notification between debuggers by detecting an error condition inthe first application (204). The error condition in the firstapplication (204) represents the occurrence of an event during which thefirst application (204) ceases to function properly. Examples of anerror condition can include the first application (204) crashing, thefirst application (204) attempting to perform an operation on a nullvalue, the first application (204) attempting to access protected orotherwise unavailable memory, and so on.

In the example of FIG. 1, the first debugger (202) can further carry outcrash notification between debuggers by determining whether anyvariables utilized by the first application (204) are related tovariables utilized by a second application (220). In the example of FIG.1, the second application (220) is embodied as a computer programexecuting on another computer (182). Variables utilized by the firstapplication (204) may be related to variables utilized by the secondapplication (220) for a variety of reasons. For example, the value of avariable utilized by the first application (204) may be generated by afunction call to the second application (220) such that the variablesutilized by the second application (220) are inputs to some operationthat generates a return value from the function call to the secondapplication (220). Likewise, the value of a variable utilized by thefirst application (204) may be generated by accessing a location inmemory that is manipulated by the second application (220) such that thevariables utilized by the second application (220) impact the value thatthe second application (220) writes to the shared location in memory. Insuch an example, determining whether any variables utilized by the firstapplication (204) are related to variables utilized by the secondapplication (220) may be carried out by determining whether the valueassigned to a variable utilized by the first application (204) aredirectly or indirectly dependent on a function call to the secondapplication (220), by determining whether the value assigned to avariable utilized by the first application (204) is dependent uponmemory that is accessible to the second application (220), and so on.

In the example of FIG. 1, the first debugger (202) can further carry outcrash notification between debuggers by communicating, to a seconddebugger (224), information associated with the error condition in thefirst application (204). In the example of FIG. 1, the second debugger(224) is executing on another computer (182) and includes a second debugsession (222) for debugging the second application (220). Theinformation associated with the error condition in the first application(204) may include, for example, information identifying the line numberat which the error condition occurred, information identifying the valueassociated with each variable being utilized by the first application(204) at the time the error condition occurred, an error codeidentifying the nature of the error condition, and so on. Communicatingthe information associated with the error condition in the firstapplication (204) may be carried out, for example, by the first debugger(202) sending a message to the second debugger (224) over a datacommunications network, by the first debugger (202) writing theinformation associated with the error condition to an area of memorythat is monitored by the second debugger (224), and so on.

Also stored in RAM (168) is an operating system (154). Operating systemsuseful crash notification between debuggers according to embodiments ofthe present invention include UNIX™ Linux™ Microsoft XP™ AIX™ IBM'si5/OS™ and others as will occur to those of skill in the art. Theoperating system (154), first debugger (202), first application (204),and first debug session (206) in the example of FIG. 1 are shown in RAM(168), but many components of such software typically are stored innon-volatile memory also, such as, for example, on a disk drive (170).

The computer (152) of FIG. 1 includes disk drive adapter (172) coupledthrough expansion bus (160) and bus adapter (158) to processor (156) andother components of the computer (152). Disk drive adapter (172)connects non-volatile data storage to the computer (152) in the form ofdisk drive (170). Disk drive adapters useful in computers for crashnotification between debuggers according to embodiments of the presentinvention include Integrated Drive Electronics (‘IDE’) adapters, SmallComputer System Interface (‘SCSI’) adapters, and others as will occur tothose of skill in the art. Non-volatile computer memory also may beimplemented for as an optical disk drive, electrically erasableprogrammable read-only memory (so-called ‘EEPROM’ or ‘Flash’ memory),RAM drives, and so on, as will occur to those of skill in the art.

The example computer (152) of FIG. 1 includes one or more input/output(‘I/O’) adapters (178). I/O adapters implement user-orientedinput/output through, for example, software drivers and computerhardware for controlling output to display devices such as computerdisplay screens, as well as user input from user input devices (181)such as keyboards and mice. The example computer (152) of FIG. 1includes a video adapter (209), which is an example of an I/O adapterspecially designed for graphic output to a display device (180) such asa display screen or computer monitor. Video adapter (209) is connectedto processor (156) through a high speed video bus (164), bus adapter(158), and the front side bus (162), which is also a high speed bus.

The example computer (152) of FIG. 1 includes a communications adapter(167) for data communications with other computers (182) and for datacommunications with a data communications network (100). Such datacommunications may be carried out serially through RS-232 connections,through external buses such as a Universal Serial Bus (‘USB’), throughdata communications networks such as IP data communications networks,and in other ways as will occur to those of skill in the art.Communications adapters implement the hardware level of datacommunications through which one computer sends data communications toanother computer, directly or through a data communications network.Examples of communications adapters useful for crash notificationbetween debuggers according to embodiments of the present inventioninclude modems for wired dial-up communications, Ethernet (IEEE 802.3)adapters for wired data communications network communications, and802.11 adapters for wireless data communications network communications.

For further explanation, FIG. 2 sets forth a flow chart illustrating anexample method for crash notification between debuggers according toembodiments of the present invention. The example method of FIG. 2includes a first debugger (202) and a second debugger (224). In theexample method of FIG. 2, the first debugger (202) and the seconddebugger (224) may be embodied, for example, as computer programs thatare utilized to test and debug other computer programs, such as a firstapplication (204) and a second application (220). In the example methodof FIG. 2, each debugger (202, 224) may be configured such that a usercan step through a target computer program to identify execution flow ofthe program, to determine the value of variables utilized by theprogram, and to identify crashes and other errors generated during theexecution of the program, and so on.

The method of FIG. 2 includes initiating (208), by the first debugger(202), a first debug session (206) of a first application (204). In theexample method of FIG. 2, the first application (204) may be embodied asa computer program that includes a set of computer program instructions.In such an example, initiating (208) a first debug session (206) of thefirst application (204) can enable a user to execute the firstapplication (204) one instruction at a time, to execute all instructionsof the first application (204) that reside between a set of breakpoints,and otherwise examine the execution of the first application (204).

In the example method of FIG. 2, initiating (208) the first debugsession (206) of the first application (204) includes registering (302)the first debug session (206) of the first application (204) in anactive debug session registry (304). The active debug session registry(304) of FIG. 2 represents an area of computer memory that includesinformation identifying one or more debug sessions that are active.Entries in the active debug session registry (304) can includeinformation identifying the application being debugged, informationidentifying the variables used by the application being debugged,information identifying areas of memory that can be accessed byapplication being debugged, information identifying data sources such asa database that can be accessed by application being debugged, and soon. In the example method of FIG. 2, registering (302) the first debugsession (206) of the first application (204) in an active debug sessionregistry (304) may be carried out, for example, by creating an entry inthe active debug session registry (304) that represents the first debugsession (206) of the first application (204).

The method of FIG. 2 also includes initiating (218), by the seconddebugger (224), a second debug session (222) of a second application(220). In the example method of FIG. 2, the second application (220) maybe embodied as a computer program that includes a set of computerprogram instructions. In such an example, initiating (218) a seconddebug session (222) of the second application (220) can enable a user toexecute the second application (220) one instruction at a time, toexecute all instructions of the second application (220) that residebetween a set of breakpoints, and otherwise examine the execution of thesecond application (220).

In the example method of FIG. 2, initiating (218) the second debugsession (222) of the second application (220) includes registering thesecond debug session (222) of the second application (220) in an activedebug session registry (304). Registering the second debug session (222)of the second application (220) may be carried out, for example, bycreating an entry in the active debug session registry (304) thatrepresents the second debug session (222) of the second application(220). In such a way, each debug session that is occurring across anetwork connected environment may become aware of all other debugsessions that are occurring on computers in the network connectedenvironment by searching the entries in the active debug sessionregistry (304).

The method of FIG. 2 also includes detecting (210), by the firstdebugger (202), an error condition in the first application (204). Inthe example method of FIG. 2, the error condition in the firstapplication (204) represents the occurrence of an event during which thefirst application (204) ceases to function properly. Examples of anerror condition can include the first application (204) crashing, thefirst application (204) attempting to perform an operation on a nullvalue, the first application (204) attempting to access protected orotherwise unavailable memory, and so on.

The method of FIG. 2 also includes determining (212), by the firstdebugger (202), whether any variables utilized by the first application(204) are related to variables utilized by the second application (220).As described above, the second application (220) is being debugged in asecond debug session (222) by a second debugger (224). In the examplemethod of FIG. 2, variables utilized by the first application (204) maybe related to variables utilized by the second application (220) for avariety of reasons. For example, the value of a variable utilized by thefirst application (204) may be generated by a function call to thesecond application (220) such that the variables utilized by the secondapplication (220) are inputs to some operation that generates a returnvalue from the function call to the second application (220). Likewise,the value of a variable utilized by the first application (204) may begenerated by accessing a location in memory that is manipulated by thesecond application (220) such that the variables utilized by the secondapplication (220) impact the value that the second application (220)writes to the shared location in memory. In such an example, determining(212) whether any variables utilized by the first application (204) arerelated to variables utilized by the second application (220) may becarried out by determining whether the value assigned to a variableutilized by the first application (204) are directly or indirectlydependent on a function call to the second application (220), bydetermining whether the value assigned to a variable utilized by thefirst application (204) is dependent upon memory that is accessible tothe second application (220), and so on.

The method of FIG. 2 also includes communicating (214), by the firstdebugger (202) to the second debugger (224), information (216)associated with the error condition in the first application (204). Inthe example method of FIG. 2, the information (216) associated with theerror condition in the first application (204) may include, for example,information identifying the line number at which the error conditionoccurred, information identifying the value associated with eachvariable being utilized by the first application (204) at the time theerror condition occurred, an error code identifying the nature of theerror condition, and so on. In the example method of FIG. 2,communicating (214) the information (216) associated with the errorcondition in the first application (204) may be carried out, forexample, by the first debugger (202) sending a message to the seconddebugger (224), by the first debugger (202) writing the information(216) associated with the error condition to an area of memory that ismonitored by the second debugger (224), and so on. By communicatinginformation (216) between such debuggers (202, 224), users of eachdebugger (202, 224) helps the user to better understand the nature ofthe problem sooner and allows them to take corrective action.

For further explanation, FIG. 3 sets forth a flow chart illustrating anadditional example method for crash notification between debuggersaccording to embodiments of the present invention. The method of FIG. 3is similar to the method of FIG. 2 as it also includes initiating (208)a first debug session (206) of a first application (204), detecting(210) an error condition in the first application (204), determining(212) whether any variables utilized by the first application (204) arerelated to variables utilized by the second application (220), andcommunicating (214) information (216) associated with the errorcondition in the first application (204) to the second debugger (224).

The example method of FIG. 3 also includes identifying (402), by thefirst debugger (202), one or more positions in the first application(204) where one or more variables utilized by the first application(204) are related to one or more variables utilized by the secondapplication (220). In the example method of FIG. 3, a position in thefirst application (204) where one or more variables utilized by thefirst application (204) are related to one or more variables utilized bythe second application (220) represents a segment of code in the firstapplication (204) where the value of one or more variables utilized bythe first application (204) may be impacted by variables utilized by thesecond application (220). Consider the following psuedocode example:

int FirstAppVariable = SecondApplication (FirstParam, SecondParam); if(FirstAppVariable >= 1)   {     ThirdApplication (FirstAppVariable);   }else   {     FourthApplication (FirstAppVariable);   } FirstAppVariable= 1;

In the first line of the code segment, an integer variable named‘FirstAppVariable’ is initialized and set to a value that is generatedby making a function call to a function named ‘SecondApplication’ thatresides in a second application. In the second line of the code segment,the value returned by the function call to the second application isutilized in evaluating a conditional statement. In the third throughfifth lines of the code segment, a function call to a function named‘ThirdApplication’ is conditionally made. In the sixth through eighthlines of the code segment, a function call to a function named‘FourthApplication’ is conditionally made. In the ninth line of the codesegment, the value of ‘FirstAppVariable’ is set to 1.

In such an example, the first through ninth lines of the code segmentrepresent positions in the first application (204) where one or morevariables utilized by the first application (204) are related to one ormore variables utilized by the second application (220). That is, in thefirst through ninth line of the example code segment, the value of‘FirstAppVariable’ is set to a value generated by a function call to thesecond application. At the tenth line of the code segment, however, thevalue of ‘FirstAppVariable’ is set to 1 during every iteration of thecode segment such that the value of ‘FirstAppVariable’ is no longerrelated to one or more variables utilized by the second application(220). In the example method of FIG. 3, identifying (402) one or morepositions in the first application (204) where one or more variablesutilized by the first application (204) are related to one or morevariables utilized by the second application (220) may therefore becarried out, for example, by automatically examining the code fordependencies, by receiving input from a user identifying code segmentsthat include dependencies, and so on.

The example method of FIG. 3 also includes determining (404), by thefirst debugger (202), a stop position in the first application (204) atwhich the error condition in the first application (204) occurred. Inthe example method of FIG. 3, the a stop position in the firstapplication (204) represents the line of code, or a range of lines,within the first application (204) at which the error condition in thefirst application (204) occurred.

In the example method of FIG. 3, determining (21) whether any variablesutilized by the first application (204) are dependent upon variablesutilized by the second application (220) includes determining (406)whether the stop position is one of the positions in the firstapplication (204) where one or more variables utilized by the firstapplication (204) are related to one or more variables utilized by thesecond application (220). In the example method of FIG. 3, determining(406) whether the stop position is one of the positions in the firstapplication (204) where one or more variables utilized by the firstapplication (204) are related to one or more variables utilized by thesecond application (220) may be carried out, for example, by comparingthe line number in a code segment for the stop position to line numbersin the code segment where one or more variables utilized by the firstapplication (204) are related to one or more variables utilized by thesecond application (220). In such a way, the first debugger (202) candetermine if the error condition occurred at a point during theexecution of the first application (204) at which variables utilized bythe first application (204) are related to one or more variablesutilized by the second application (220).

In situations in which the error condition occurred at a point duringthe execution of the first application (204) at which variables utilizedby the first application (204) are related to one or more variablesutilized by the second application (220), the second application (220)may be responsible for the error condition encountered in the firstapplication (204). That is, the error condition that was encountered inthe first application (204) may be the result of the second application(220) improperly manipulating a variable that is related to a variableutilized by the first application (204). Consider the example psuedocodeincluded above that includes the following statements:

int FirstAppVariable = SecondApplication (FirstParam, SecondParam); if(FirstAppVariable >= 1) ...

If the function call to ‘SecondApplication’ resulted in the return of anull value, an error condition may be encountered in the second line ofthe code segment when an attempt is made to determine whether a value ofnull is greater than or equal to an integer value of 1. In such anexample, the debugger that is analyzing this code segment in the firstapplication will raise an error condition. The cause of the errorcondition, however, is possibly the result of some erroneous codesegments in the second application that returned a null value ratherthan an integer value as expected by the first application.

For further explanation, FIG. 4 sets forth a flow chart illustrating anadditional example method of crash notification between debuggersaccording to embodiments of the present invention. The method of FIG. 4is similar to the method of FIG. 2 as it also includes initiating (208)a first debug session (206) of a first application (204), detecting(210) an error condition in the first application (204), determining(212) whether any variables utilized by the first application (204) arerelated to variables utilized by the second application (220), andcommunicating (214) information (216) associated with the errorcondition in the first application (204) to the second debugger (224).

In the example method of FIG. 4, the information (216) associated withthe error condition in the first application (204) can include a linenumber (502) in the first application at which the error conditionoccurred. In such an example, the line number (502) in the firstapplication at which the error condition occurred can be used toidentify the variables utilized by the second application (220) that arerelated to variables that were utilized by the first application (204)at the time that the error condition was encountered. For example, thecode in the first application (204) that is identified by the linenumber (502) may be examined to identify a function call to the secondapplication (220), a reference to memory or a data structure that isutilized by the second application (220), and so on. The information(216) associated with the error condition in the first application (204)could also include the names and values (502) of variables in the firstapplication (204) that are related to variables in the secondapplication (220), as well as other information as will occur to thoseof skill in the art.

In the example method of FIG. 4, the information (216) associated withthe error condition in the first application (204) can also include thenames and values (504) of variables in the second application (220) thatare related to variables in the first application (204). In the examplemethod of FIG. 4, the names and values (504) of variables in the secondapplication (220) that are related to variables in the first application(204) may be embodied as identifiers of the variables, pointers to thevariables, memory locations for the variables, and so on.

Example embodiments of the present invention are described largely inthe context of a fully functional computer system for crash notificationbetween debuggers. Readers of skill in the art will recognize, however,that the present invention also may be embodied in a computer programproduct disposed upon computer readable storage media for use with anysuitable data processing system. Such computer readable storage mediamay be any storage medium for machine-readable information, includingmagnetic media, optical media, or other suitable media. Examples of suchmedia include magnetic disks in hard drives or diskettes, compact disksfor optical drives, magnetic tape, and others as will occur to those ofskill in the art. Persons skilled in the art will immediately recognizethat any computer system having suitable programming means will becapable of executing the steps of the method of the invention asembodied in a computer program product. Persons skilled in the art willrecognize also that, although some of the example embodiments describedin this specification are oriented to software installed and executingon computer hardware, nevertheless, alternative embodiments implementedas firmware or as hardware are well within the scope of the presentinvention.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as JAVA programming language, Smalltalk, C++ or the like andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

What is claimed is:
 1. An apparatus for crash notification betweendebuggers, the apparatus comprising a computer processor, a computermemory operatively coupled to the computer processor, the computermemory having disposed within it computer program instructions that,when executed by the computer processor, cause the apparatus to carryout the steps of: initiating, by a first debugger, a first debug sessionof a first application; detecting, by the first debugger, an errorcondition in the first application; identifying, by the first debugger,one or more positions in the first application where one or morevariables utilized by the first application are related to one or morevariables utilized by the second application; determining, by the firstdebugger, a stop position in the first application at which the errorcondition in the first application occurred; and determining, by thefirst debugger, whether any variables utilized by the first applicationare related to variables utilized by a second application, wherein thesecond application is being debugged in a second debug session by asecond debugger; wherein determining whether any variables utilized bythe first application are dependent upon variables utilized by thesecond application further comprises determining whether the stopposition is one of the positions in the first application where one ormore variables utilized by the first application are related to one ormore variables utilized by the second application; and communicating, bythe first debugger to a second debugger, information associated with theerror condition in the first application.
 2. The apparatus of claim 1wherein initiating the first debug session of the first applicationfurther comprises registering the first debug session of the firstapplication in an active debug session registry.
 3. The apparatus ofclaim 1 further comprising computer program instructions that, whenexecuted by the computer processor, cause the apparatus to carry out thestep of initiating, by the second debugger, the second debug session ofthe second application, including registering the second debug sessionof the second application in an active debug session registry.
 4. Theapparatus of claim 1 wherein the information associated with the errorcondition in the first application includes a line number in the firstapplication at which the error condition occurred.
 5. The apparatus ofclaim 1 wherein the information associated with the error condition inthe first application includes the names and values of variables in thesecond application that are related to variables in the firstapplication.
 6. A computer program product for crash notificationbetween debuggers, the computer program product disposed upon anon-transitory computer readable medium, the computer program productcomprising computer program instructions that, when executed, cause acomputer to carry out the steps of: initiating, by a first debugger, afirst debug session of a first application; detecting, by the firstdebugger, an error condition in the first application; identifying, bythe first debugger, one or more positions in the first application whereone or more variables utilized by the first application are related toone or more variables utilized by the second application; determining,by the first debugger, a stop position in the first application at whichthe error condition in the first application occurred; and determining,by the first debugger, whether any variables utilized by the firstapplication are related to variables utilized by a second application,wherein the second application is being debugged in a second debugsession by a second debugger; wherein determining whether any variablesutilized by the first application are dependent upon variables utilizedby the second application further comprises determining whether the stopposition is one of the positions in the first application where one ormore variables utilized by the first application are related to one ormore variables utilized by the second application; and communicating, bythe first debugger to a second debugger, information associated with theerror condition in the first application.
 7. The computer programproduct of claim 6 wherein initiating the first debug session of thefirst application further comprises registering the first debug sessionof the first application in an active debug session registry.
 8. Thecomputer program product of claim 6 further comprising computer programinstructions that, when executed, cause the computer to carry out thestep of initiating, by the second debugger, the second debug session ofthe second application, including registering the second debug sessionof the second application in an active debug session registry.
 9. Thecomputer program product of claim 6 wherein the information associatedwith the error condition in the first application includes a line numberin the first application at which the error condition occurred.
 10. Thecomputer program product of claim 6 wherein the information associatedwith the error condition in the first application includes the names andvalues of variables in the second application that are related tovariables in the first application.